You can use the IDS Data Management form to import and export LDAP Data Interchange Format (LDIF) files.
The import operation allows you to add LDIF file data to the MiVoice Business contact point. The LDIF files can originate from the directory server, be created as part of an IDS synchronization event, or be created by some other means. Provided that the files adhere to the LDIF standards laid out in RFC 2849, they can be imported to MiVoice Business. Note that only add, modify, and delete instructions are supported.
To import an LDIF file to the MiVoice Business contact point:
Save the LDIF file in a folder that is accessible to MiVoice Business. The file must adhere to RFC 2849.
Go to the IDS
Data Management form.
Click LDIF File Import.
The Import dialog displays.
Click Browse.
Navigate to the location of the LDIF file and select it.
Click Import.
The file is uploaded.
The export operation allows you to export LDIF file data from the MiVoice Business contact point and its associated SDS network. The following files are exported:
IDSManagedUsersWithDomainX_<date_timestamp>.ldf — This file contains IDS-manageable records that have domain data and therefore exist on both the SDS network and the directory server. Use this file to update the directory server with the latest user and device data (including modification instructions) from the SDS network. A separate file is created for each domain host.
IDSManagedUsersWithNoDomain_<date_timestamp>.ldf — This file lists IDS-manageable records that do not have domain data and therefore exist only on the SDS network. Use this file to update the directory server with new user records from the SDS network.
NonIDSManagedUsers_<date_timestamp>.ldf — This file lists records that are not IDS manageable. Use this file to determine which users are managed solely on the SDS network. To enable a user to be IDS manageable, open the user record from the User and Services Configuration form and select the "IDS-Manageable" field.
NOTE: The IDS-Manageable flag is not included in the exported LDIF files.
To export LDIF files from the MiVoice Business contact point:
Go to the IDS
Data Management form.
Click LDIF File Export.
The Export dialog displays.
(Optional) Enter a directory path in Distinguished Name (DN) format to apply to records contained in the second LDIF file (IDSManagedUsersWithNoDomain_<date_timestamp>.ldf).
This information is used to construct a DN for each user object, specifying its location in the directory tree. After exporting the file, you can edit it if necessary (by adding unique parents/directory paths to user objects) and then import it onto a directory server.
When entering a DN, bear in mind that special characters (, = + < > # ; \ ") must be preceded with a \ sign.
Example 1 — Users objects in the Users folder in the mitel.com domain:
CN=Users,DC=mitel,DC=com
Example 2 — Users objects in the RD organizational subfolder of the Engineering organizational unit folder in the mitel.com domain:
OU=RD,OU=Engineering,DC=mitel,DC=com
Example 3 — Users objects in "RD, ENG" folder (using special characters) in the mitel.com domain:
OU=\"RD\, ENG\",DC=mitel,DC=com
(Optional) Select the Exclude User Id Data check box to exclude the User ID from the exported data.
Do this if the LDIF files will be used to update the DS via file import and the User ID is mapped to a system-protected attribute such as the AD objectGuid attribute. (The file import operation on the DS will fail if the file contains system-protected data.) Clear the check box to include the User ID in the exported data. Do this if the LDIF files will be used to update user data on MiVoice Business.
NOTE: Although it is possible to update user data on MiVoice Business by importing an LDIF file, it is preferable to make these changes via the User and Services Configuration form.
Click Export. The LDIF files are collected into a single tar archive file.
When the File Download dialog box appears, click Save. Navigate to a folder on your computer to save the archive file.
Use a utility such as WinZip to extract the LDIF files from the archive file.